| Package | hl7.ehrs.uv.phrsfmr2 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-S.3.2.html |
| Url | http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-S.3.2 |
| Version | 2.0.1-ballot |
| Status | active |
| Date | 2025-04-03T15:15:30+00:00 |
| Name | S_3_2_Manage_PHR_Conditions_of_Use |
| Title | S.3.2 Manage PHR Conditions of Use (Function) |
| Experimental | False |
| Authority | hl7 |
| Description | Outline the sponsor requirements for use of the system. |
| Purpose | The terms and conditions outline the sponsor requirements in using the application. The terms and conditions may include items such as copyright information, trademarks and intellectual property, third party links, indemnification, privacy, limitation of liability, term and termination and other miscellaneous provisions. The PHR Account Holder should be notified of the expectations of the sponsor and have the opportunity to agree to the requirements and any changes to the requirements. The Conditions of Use document also helps indemnify the PHR sponsor against certain misuse of the data. For example, a published article on diabetes may contain a copyright notice that forbids the storage of that article on a computer without first paying for the article. The Conditions of Use document would inform the PHR Account Holder that the sponsor does not support copyright infringement. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Outline the sponsor requirements for use of the system.
The terms and conditions outline the sponsor requirements in using the application. The terms and conditions may include items such as copyright information, trademarks and intellectual property, third party links, indemnification, privacy, limitation of liability, term and termination and other miscellaneous provisions. The PHR Account Holder should be notified of the expectations of the sponsor and have the opportunity to agree to the requirements and any changes to the requirements.
The Conditions of Use document also helps indemnify the PHR sponsor against certain misuse of the data. For example, a published article on diabetes may contain a copyright notice that forbids the storage of that article on a computer without first paying for the article. The Conditions of Use document would inform the PHR Account Holder that the sponsor does not support copyright infringement.
| S.3.2#01 | SHOULD |
The system SHOULD provide the ability for the PHR Account Holder to enter an indication of an agreement to the Conditions-of-Use when the PHR-S is initially used by the PHR Account Holder. |
| S.3.2#02 | dependent SHALL |
The system SHALL render a notification to the PHR Account Holder that changes occurred to the Conditions-of-Use documents according to organizational policy and/or jurisdictional law. |
| S.3.2#03 | dependent SHOULD |
The system SHOULD provide the ability to present changes that occurred to the Conditions-of-Use documents (e.g., the actual document, or an audit, or a summary, or an overview of the changes) according to organizational policy and/or jurisdictional law. |
| S.3.2#04 | SHOULD |
The system SHOULD provide the ability to render the Conditions-of-Use. |
| S.3.2#05 | SHALL |
The system SHALL provide the ability for the PHR Account Holder to render a notification to the PHR-S vendor and/or sponsor(s) as part of the process to seek redress regarding the vendor and/or sponsor‘s failure to meet performance expectations as specified in the Conditions-of-Use agreements (including reporting PHR-S errors, failures, abuse, fraud, or other issues). |
| S.3.2#06 | SHOULD |
The system SHOULD provide the ability to maintain a list of PHR-S administrators and personnel to receive, manage, and respond to emails and telephone calls regarding PHR-S errors, failures, abuse, fraud, or any other PHR Account Holder issues with the PHR-S Terms and Conditions-of-Use agreements. |
FHIR{
"resourceType" : "Requirements",
"id" : "PHRSFMR2-S.3.2",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Outline the sponsor requirements for use of the system.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>The terms and conditions outline the sponsor requirements in using the application. The terms and conditions may include items such as copyright information, trademarks and intellectual property, third party links, indemnification, privacy, limitation of liability, term and termination and other miscellaneous provisions. The PHR Account Holder should be notified of the expectations of the sponsor and have the opportunity to agree to the requirements and any changes to the requirements.</p>\n<p>The Conditions of Use document also helps indemnify the PHR sponsor against certain misuse of the data. For example, a published article on diabetes may contain a copyright notice that forbids the storage of that article on a computer without first paying for the article. The Conditions of Use document would inform the PHR Account Holder that the sponsor does not support copyright infringement.</p>\n</div></span>\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> ehr</span>\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.3.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability for the PHR Account Holder to enter an indication of an agreement to the Conditions-of-Use when the PHR-S is initially used by the PHR Account Holder.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.3.2#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL render a notification to the PHR Account Holder that changes occurred to the Conditions-of-Use documents according to organizational policy and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.3.2#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to present changes that occurred to the Conditions-of-Use documents (e.g., the actual document, or an audit, or a summary, or an overview of the changes) according to organizational policy and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.3.2#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render the Conditions-of-Use.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.3.2#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability for the PHR Account Holder to render a notification to the PHR-S vendor and/or sponsor(s) as part of the process to seek redress regarding the vendor and/or sponsor‘s failure to meet performance expectations as specified in the Conditions-of-Use agreements (including reporting PHR-S errors, failures, abuse, fraud, or other issues).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>S.3.2#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to maintain a list of PHR-S administrators and personnel to receive, manage, and respond to emails and telephone calls regarding PHR-S errors, failures, abuse, fraud, or any other PHR Account Holder issues with the PHR-S Terms and Conditions-of-Use agreements.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "ehr"
}
],
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-S.3.2",
"version" : "2.0.1-ballot",
"name" : "S_3_2_Manage_PHR_Conditions_of_Use",
"title" : "S.3.2 Manage PHR Conditions of Use (Function)",
"status" : "active",
"date" : "2025-04-03T15:15:30+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Outline the sponsor requirements for use of the system.",
"purpose" : "The terms and conditions outline the sponsor requirements in using the application. The terms and conditions may include items such as copyright information, trademarks and intellectual property, third party links, indemnification, privacy, limitation of liability, term and termination and other miscellaneous provisions. The PHR Account Holder should be notified of the expectations of the sponsor and have the opportunity to agree to the requirements and any changes to the requirements.\r\n\r\nThe Conditions of Use document also helps indemnify the PHR sponsor against certain misuse of the data. For example, a published article on diabetes may contain a copyright notice that forbids the storage of that article on a computer without first paying for the article. The Conditions of Use document would inform the PHR Account Holder that the sponsor does not support copyright infringement.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-S.3.2-01",
"label" : "S.3.2#01",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability for the PHR Account Holder to enter an indication of an agreement to the Conditions-of-Use when the PHR-S is initially used by the PHR Account Holder."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "PHRSFMR2-S.3.2-02",
"label" : "S.3.2#02",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL render a notification to the PHR Account Holder that changes occurred to the Conditions-of-Use documents according to organizational policy and/or jurisdictional law."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "PHRSFMR2-S.3.2-03",
"label" : "S.3.2#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to present changes that occurred to the Conditions-of-Use documents (e.g., the actual document, or an audit, or a summary, or an overview of the changes) according to organizational policy and/or jurisdictional law."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-S.3.2-04",
"label" : "S.3.2#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render the Conditions-of-Use."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-S.3.2-05",
"label" : "S.3.2#05",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability for the PHR Account Holder to render a notification to the PHR-S vendor and/or sponsor(s) as part of the process to seek redress regarding the vendor and/or sponsor‘s failure to meet performance expectations as specified in the Conditions-of-Use agreements (including reporting PHR-S errors, failures, abuse, fraud, or other issues)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-S.3.2-06",
"label" : "S.3.2#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to maintain a list of PHR-S administrators and personnel to receive, manage, and respond to emails and telephone calls regarding PHR-S errors, failures, abuse, fraud, or any other PHR Account Holder issues with the PHR-S Terms and Conditions-of-Use agreements."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.